An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

I'm trying to submit my app version together with two auto-renewable subscriptions (both in the same subscription group), and one of the two subscriptions will not submit, while the other submits with no issue. Setup One subscription group ("Crucibull Pro") with two subscriptions: Annual — $49.99/year — submits fine Weekly — $1.99/week — fails to submit Both are being submitted together with a new app build in a single review submission. The errors I get (they vary, none are field-specific) "There are errors with one or more of your items. To fix them, you need to remove the items and add them again to your submission." "Sorry, something went wrong. Try your request again." "An unexpected error was encountered when submitting for review. If the issue persists please contact us." Critically, there is no red/field-level error anywhere on the Weekly subscription's page — its status is "Prepare for Submission" and every field is filled. What I've tried (nothing has worked) Verified every field on Weekly: reference name, product ID, 1-week duration, availability (all countries), price ($1.99 with a valid start date), localization (display name + description), tax category, and an App Review screenshot. Compared Weekly side-by-side with Annual (which submits fine) and matched every field. Changed Weekly's Tax Category to "Match to parent app" to match Annual. Removed and re-added the items to the submission (per the error message's advice) multiple times. Configured the subscription group ranking/levels. Deleted the original Weekly subscription and recreated it from scratch with a new Product ID — same result. Confirmed App Store Connect is stable (System Status all green) and still errors. Tried fresh submissions, different browser/incognito, and re-uploading the screenshot. Current state The Annual sub and the app build are ready and submit fine. The Weekly sub is fully configured, identical to Annual, freshly recreated, on a stable platform — and still throws generic submission errors with no indication of what's actually wrong. Question Has anyone seen an auto-renewable subscription that's fully configured (and identical to a working one in the same group) fail to submit with only generic errors and no field-level detail? Is there a known backend/propagation issue, or a hidden requirement I'm missing? Any way to see the actual validation failure? Thanks in advance.

Hi App Review, An update to an app that's already live on the App Store has been in "Waiting for Review" for 10 days with no status change, and I wanted to check whether it's proceeding normally or whether anything is required from my side. Submission ID: b4e5d54c-de30-4003-9f3c-232e366d01c4 Version: 1.1.0 (build 7), an update to a live app (1.0.0 currently in production) Submitted: 16 June 2026, 22:10 Current status: Waiting for Review (has not moved to In Review) I've already checked the usual things my end: there's no message in Resolution Center, no "action required" banner on the app or version page, the build shows as valid and is correctly attached to the version, export compliance/encryption is answered, and Agreements, Tax, and Banking are all current. I also contacted Developer Support via the contact form on 23 June [add: case #102923511308 if you have one] but haven't had a reply yet. Could you confirm whether the review is proceeding normally, or let me know if there's anything I need to do? Happy to provide any further detail. Thanks.

I'm trying to submit my app version together with two auto-renewable subscriptions (both in the same subscription group), and one of the two subscriptions will not submit, while the other submits with no issue. Setup One subscription group ("Crucibull Pro") with two subscriptions: Annual — $49.99/year — submits fine Weekly — $1.99/week — fails to submit Both are being submitted together with a new app build in a single review submission. The errors I get (they vary, none are field-specific) "There are errors with one or more of your items. To fix them, you need to remove the items and add them again to your submission." "Sorry, something went wrong. Try your request again." "An unexpected error was encountered when submitting for review. If the issue persists please contact us." Critically, there is no red/field-level error anywhere on the Weekly subscription's page — its status is "Prepare for Submission" and every field is filled. What I've tried (nothing has worked) Verified every field on Weekly: reference name, product ID, 1-week duration, availability (all countries), price ($1.99 with a valid start date), localization (display name + description), tax category, and an App Review screenshot. Compared Weekly side-by-side with Annual (which submits fine) and matched every field. Changed Weekly's Tax Category to "Match to parent app" to match Annual. Removed and re-added the items to the submission (per the error message's advice) multiple times. Configured the subscription group ranking/levels. Deleted the original Weekly subscription and recreated it from scratch with a new Product ID — same result. Confirmed App Store Connect is stable (System Status all green) and still errors. Tried fresh submissions, different browser/incognito, and re-uploading the screenshot. Current state The Annual sub and the app build are ready and submit fine. The Weekly sub is fully configured, identical to Annual, freshly recreated, on a stable platform — and still throws generic submission errors with no indication of what's actually wrong. Question Has anyone seen an auto-renewable subscription that's fully configured (and identical to a working one in the same group) fail to submit with only generic errors and no field-level detail? Is there a known backend/propagation issue, or a hidden requirement I'm missing? Any way to see the actual validation failure? Thanks in advance.

Hi all, I’m hoping someone from Apple or the community can help. Our app Lazy Watch (Bundle ID: app.lazywatch) has a build stuck in “Waiting for Beta Review” since Saturday, July 11 at 3:07 AM — it’s now been 6 days with no movement. Details: • Build: 0.0.1 (5) • Binary State: Validated • Non-Exempt Encryption: No (export compliance answered) • Test Information: fully filled out • No messages in Resolution Center I’ve tried reaching Developer Support multiple times through the Contact Us form (both phone “Call me” and email routes) with no response and no callback. This is well beyond the normal 24–48 hour review window and is currently blocking our launch plans. Could someone from App Review or WWDR take a look, or point me to the right escalation path? Happy to provide any additional details needed. Thanks in advance.

Hello, We received Guideline 2.1 information requests for Proxima during the previous App Review cycle. We provided detailed answers and, on July 17, uploaded and resubmitted corrected build 15 for iOS, tvOS, and macOS. The new App Store binary completely removes account, subscription, pricing, purchase, renewal, external payment, and provider-specific backend functionality. Proxima is now a free, provider-independent client that only imports configurations supplied by the user. It does not sell or provide VPN access, require an account, collect analytics, log traffic, or share user data. All three build 15 submissions are valid and App Store eligible, and all are currently Waiting for Review. We also updated the App Review notes with exact testing and data-handling information and followed up through Apple Developer Support. The previous Resolution Center threads no longer accept developer replies after resubmission. Is there any additional action we should take to make sure the corrected submissions are not blocked? If an Apple staff member can confirm that the submissions are properly queued or route them to the appropriate App Review team, we would be very grateful. The release is time-sensitive, and we can answer any additional questions immediately. Thank you.

Hi my app is still "Waiting for Review" since almost a week now. Is it normal? Thank you!

Hello everyone, We have a SaaS product and are currently transitioning our business model. Previously, we used a standard recurring subscription model implemented via StoreKit 2 in our iOS app. Recently, we changed our pricing to a performance-based model, where we charge a percentage fee based on the user's specific usage and performance. On our web platform, we use Stripe to calculate and accept these dynamic percentage-based payments. I have two questions regarding this transition for our iOS app: Payment Gateway: Since our new pricing model is a variable, performance-based percentage rather than a fixed subscription, does Apple allow us to integrate Stripe directly into the iOS app to process these payments? The service provided is digital. Removing Old Subscriptions: We have completely commented out all StoreKit code in our app build since we are no longer offering those plans. However, we cannot find a "Delete" option in App Store Connect to remove the old subscription items. What is the proper way to completely remove these from our app's backend and store listing? Any guidance on the best way to handle this transition and remain compliant with App Review would be greatly appreciated. Thank you!

Hi everyone, I'm looking to see if there is a current queue backlog or if an Apple representative might be able to take a look at our status. Our game's very first external TestFlight build has been sitting in "Waiting for Review" with no movement. App Name: Pippin Plaza - 4 Player Co-op App ID: 6787434739 Version & Build: Version 1.0 (Build 2) Submitted: July 15, 2026 Current Status: Waiting for Review The Test Information metadata, contact details, and App Tracking Transparency prompts are fully detailed and filled out. Are any other indie developers experiencing multi-day TestFlight delays this week, or is this standard for a first-time external version review right now? Any insight or visibility from Apple would be deeply appreciated!

I submitted my app, PerkPulse, for review and it got rejected due to EULA agreement not being in app description, and for the subscriptions not being attached to the subscription. Currently, when I try to submit my app and two subscriptions, I get the error, "There are errors with one or more of your items. To fix them, you need to remove the items and add them again to your submission." and it highlights one of my subscriptions. This is very frustrating and is blocking me from submitting my app for review. PerkPulse Pro Annually - product ID: app.perkpulse.mobile.pro_annual_v3 PerkPulse Pro Month - product ID: app.perkpulse.mobile.pro_monthly_v3 When I open the subscription group, it shows as "In Review", but I do not see any option for removing it from review so that I can attach my subscriptions. I have also had a phone call with apple support and could not get the issue resolved. I have: Deleted and recreated the subscriptions Checked all input fields, agreements to sign, etc. and cannot find an empty field Removed and re-added the subscriptions to draft submission Please any help would be appreciated.

Hello, I'm looking for advice from other developers who may have experienced unusually long App Review times. Here is my situation: • I submitted five apps on March 2, 2026. • They remained in Waiting for Review until the end of April. • They have now been In Review for several months. • I also submitted CampusGo Connect on May 14, 2026, and it is still Waiting for Review. I have contacted Apple Developer Support several times. They confirmed that my apps are still in the review process, but there have been no updates or requests for additional information. I have also verified that my Apple Developer Program membership is active, all agreements are accepted, and my App Store Connect account is functioning normally. Has anyone experienced review times this long? If so: • How long did your review eventually take? • Was there anything you did that helped? • Is there anything else I should try besides continuing to work with Developer Support? Thank you for any advice.

Hi, I just wanted to post to see if anyone else is experiencing extremely poor customer support from Apple. I have sent emails regarding the delay for the app review and heard nothing back, I have tried to call the worldwide support but get stuck in queues for over 3 hours before being disconnected. Has it always been this poor? My app has been stuck in review now for over a week despite it saying 48 hours, and whenever I try to reach out for help I receive no response. Could anyone please advise. Thank you!

Hi, I just wanted to reach out and see if anyone else is having a really poor apple experience like myself. I submitted my app over a week ago and it's just been stuck on 'Waiting for a Review'. I've sent emails requesting an update over a week ago and heard nothing back! And I have even tried to call in using the Worldwide Telephone Support but have been stuck on queue times over 3 hours before getting disconnected! Is it common for Apple Developer Support to be this poor? I just feel as if I am extremely stuck now and the lack of communication from Apple is impossible to understand what is going on, especially given they say 48 hours but we are significantly over that period. Ever since I paid to be on the Apple Developer Program I've had no help or communication from Apple Support.

I submitted my app for review through App Store Connect two days ago, but the status has remained “Waiting for Review” without any updates. All required app information, agreements, compliance details, screenshots, and review notes have been completed. I have not received any messages indicating that additional action is required. Is this review waiting time currently normal, or should I contact App Review Support? Has anyone recently experienced a similar delay? Any advice or suggestions would be greatly appreciated.

My app was rejected because the Age Rating metadata did not correctly indicate that the app includes User-Generated Content. I have now updated the App Store Connect information accordingly and corrected the age rating selections as requested. I have been waiting quite a long time for the review process, and didnt recive any updates should I do anything else or is there any way to make the process faster?

We are in urgent need of advice or escalation regarding our app review status. Our app has been stuck in the "Waiting for Review" status for several days. Due to a critical technical emergency, we submitted an Expedited App Review Request over 48 hours ago, but we have yet to receive any response or status update. Here are the critical details of our current situation: The Critical Bug: We recently had to deploy an emergency server-side architecture upgrade. As a result, a severe incompatibility bug has occurred between the legacy client app and the live server. The Impact: Currently, 100% of our active users are completely blocked from logging into the game, and all In-App Purchases (IAP) are broken. Our live operations have completely ground to a halt. We have double-checked that this emergency build complies with all App Store Review Guidelines, and all test credentials in App Store Connect are active. If any Apple Forum Moderation Team member or Community Manager sees this, we humbly request your assistance to help us look into this case or escalate it to the App Review team. Our team and our user community are deeply impacted by this prolonged outage. Expedited Request Case ID: 102941404580 Thank you so much for your time and help.

I have implemented subscription renewals in my app and now want to integrate a referral system. Each user should receive a unique referral code that they can share with others. When a new user signs up using a referral code, both the referrer and the referred user should receive a bonus. What is the best approach to implementing this feature efficiently?

Hi all — hoping someone from the App Review team can help with this. App: ContentCam: Dual Camera Video (App ID 1281521467) Submitted two auto-renewable subscriptions (Annual + Monthly) under subscription group "ContentCam Premium" over a week ago (App version 2.0 as well as 2.0.1). App version 2.0 and 2.0.1 was reviewed and approved independently. The subscriptions have not moved from "Waiting for Review" despite the binary being approved. No rejection message, no metadata flag, nothing actionable showing on my end. This matches reports I've seen from other developers here: once an app version is rejected and later resubmitted/approved, the attached subscriptions can get stuck in "Waiting for Review" indefinitely, disconnected from the binary review outcome. I've contacted Apple Developer Support (case open, no resolution yet). Posting here in case this needs engineering visibility, or if anyone has a workaround that's actually worked (not just "wait" or "resubmit a new build" — already tried the latter with no effect). Thanks in advance.

My DSA has been in review since June Digital Services Act 27 Countries or Regions View Jun 1, 2026 In Review How long does this take? I don't understand why it's taking so long. Should we just skip European countries from our apps from now on?

Hello, My name is Tarek Mansour. I've been developing for Apple platforms since before the App Store existed, and my developer account dates back to the year the store launched. I say that only to make one point: I know how this process is supposed to work, and this is not it. My app has been sitting in "Waiting for Review" for over three weeks. It's been on the App Store for more than 10 years with a clean history. The submission in question is a critical bug fix — real users are affected every day it sits there. Every official channel has failed: • Expedited Review Request • Contact Us email • Phone support — hours on hold, no resolution Promised by email more than once that it would be handled — nothing changed Submission ID: 891c1b55-f353-4bf8-bb81-609b1c29a5cc In nearly two decades on this platform I have never seen apps left in the queue for a month with no communication and no working escalation path. Judging by this subtopic, I'm far from the only one. Apple: developers build businesses on the assumption that review is predictable and support is reachable. Right now, neither is true. Please look at this submission — and please address what's happening to the queue generally.

We submitted our banking application, Summit Bank, for review on 8 July. Since then, we have received the notification “Summit Bank Submission (iOS) version 1.3.0 has been approved” on three (3) separate occasions. However, each approval has been followed by the app remaining indefinitely in “In Review,” instead of "Pending Developer Release" forcing us to resubmit the same version repeatedly. Application Details App Name: Summit Bank Apple App ID: 6751147180 Version: 1.3.0 Current Submission ID: dfea3890-a0bf-4136-b5ae-7241db7d15c9 In our most recent submission, we included detailed notes describing this recurring issue and requesting assistance. Unfortunately, despite the app once again being marked as approved, its status has not changed and it remains stuck in the review process. This unresolved issue is causing significant operational disruption, reputational damage, and loss of business, as our customers are unable to access the latest version of the application. We respectfully request that this matter be escalated for immediate investigation and resolution. If there is any issue with our submission or additional action required on our part, please let us know as soon as possible. We would appreciate your urgent assistance in resolving this matter.